<h2>Why is this an issue?</h2>
<p>An empty interface is equivalent to an empty object ('{}'). Normally you cannot directly assign an object literal to a type when the object literal
contains more properties than are specified in the type. But in the case of an empty interface, this check is not done, and such assignments will be
successful. The result is highly likely to confuse maintainers.</p>
<h3>Noncompliant code example</h3>
<pre>
interface A {}  // Noncompliant
</pre>
<h3>Compliant solution</h3>
<pre>
interface A {
  foo: number;
}
</pre>
<h3>Exceptions</h3>
<p>No issue is raised if the empty interface extends a <a href="https://www.typescriptlang.org/docs/handbook/utility-types.html">TypeScript utility
type</a>.</p>
<pre>
interface A {
  foo: number;
  bar: string;
}

interface B extends Pick&lt;A, 'foo'&gt; {}
</pre>
<h2>Resources</h2>
<h3>Documentation</h3>
<ul>
  <li> <a href="https://typescript-eslint.io/">typescript-eslint</a> - Rule <a
  href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-empty-interface.mdx">no-empty-interface</a> </li>
</ul>
